Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1799

reference
249-tree-1
name
1799
tree-preservation-order

undefined

249-tpo-1
uprn
address-text
point
POINT (-1.010785 50.852435)
geometry
MULTIPOLYGON (((-1.010714 50.852428,-1.010717 50.852442,-1.010727 50.852454,-1.010742 50.852465,-1.010762 50.852471,-1.010784 50.852473,-1.010806 50.852471,-1.010826 50.852465,-1.010842 50.852455,-1.010852 50.852443,-1.010856 50.852429,-1.010853 50.852415,-1.010843 50.852403,-1.010827 50.852392,-1.010808 50.852386,-1.010786 50.852384,-1.010764 50.852386,-1.010744 50.852392,-1.010728 50.852402,-1.010717 50.852414,-1.010714 50.852428)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL